We are intermittently getting the following error in Exchange management console when we try to create a mailbox: The Exchange server address list service failed to respond. This could be because of an address list or email address policy configuration error. Exchange Management Shell command attempted: New-Mailbox -Name 'Test MB' -Alias 'Test.MB' -OrganizationalUnit 'nrc.ac.uk/Staff/User Accounts/Newtownabbey/Support Staff/ICT Infrastructure' -UserPrincipalName 'Test.MB@nrc.ac.uk' -SamAccountName 'Test.MB' -FirstName 'Test' -Initials '' -LastName 'MB' -Password 'System.Security.SecureString' -ResetPasswordOnNextLogon $false -Database 'NA-EXCH-MB\Staff Storage Group\Staff Database A' I've researched this on the Internet and the most common cause of this problem, it seems, was a leap year bug affecting people on 29th February 2008. Obviously this is not the case here, as that date has now passed and that bug was fixed with SP1 Rollup 5 and we're on SP1 Rollup 8. I installed Rollup 8 about three weeks ago and the issue did start to occur around then. I think it most likely that it is caused by the installation of Rollup 8. The workaround we are currently using is to restart the Microsoft Exchange System Attendant service, but this only lasts for half an hour or so before the problem returns. Could someone please help me get to the bottom of this problem ? Please find below details: Windows Server 2003 Enterprise x64 SP2 Microsoft Exchange Server 2007 SP1 w Rollup 8 Mailbox role: 2 x clustered servers Client Access and Hub Transport roles: 2 x servers (external and internal) Total of 4 Exchange servers in topology 3 x mailbox databases Rollup 8 recently installed (about 3 weeks ago) I have taken the following actions in my investigation: Tested the scenario against different mailbox databases. If this problem occurs against one database, and I test in the same way against another database, the problem usually won't occur on it as well. So far, only one database has been affected at a time, and it may be that the only database that is ever affected is 'Staff Database A'. Installed all the latest Microsoft Updates (Windows, etc) on all four servers and restarted them. Checked all event logs and can find no pertinent information. In particular there are no Application logs for Microsoft Exchange System Attendant Mailbox. There are logs for MSExchangeSA, but they are not recent and are not errors. Checked all the address lists under Microsoft Exchange / Organization Configuration / Mailbox / Address Lists. They all look OK and the criteria shouldn't have been changed. I can preview the results for all of them except the Global Address Lists. As far as address lists are concerned, they seem to be functioning ok. Can someone please help ? "Keep a cool head and always carry a lightbulb."

We are also unable to create new or enable mail on existing user accounts since Rollup 8.Windows Server 2003 Enterprise x64 SP2Microsoft Exchange Server 2007 SP1 w Rollup 8 appliedMailbox role: All, 1 serverLast friday (June 19), i was able to create 2 new mailboxes for our users. That evening we installed the Windows Server 2003 updates:Security Update for Windows Server 2003 x64 Edition (KB961501)Update Rollup for ActiveX Killbits for Windows Server 2003 x64 Edition (KB969898)Security Update for Windows Server 2003 x64 Edition (KB970238)Security Update for Windows Server 2003 x64 Edition (KB968537)Security Update for Windows Server 2003 x64 Edition (KB970483)Windows Malicious Software Removal Tool x64 - June 2009 (KB890830)Cumulative Security Update for Internet Explorer 7 for Windows Server 2003 x64 Edition (KB969897)RebootedUninstalled Update Rollup 7 for Exchange Server 2007 Service Pack 1 (KB960384)RebootedInstalled Update Rollup 8 for Exchange Server 2007 Service Pack 1 (KB968012)Just received a request today to create a new mailbox and discovered we are unable to create a new user or mailbox for an existing user on any of our mail stores.I think I'm going to attempt to uninstall rollup 8 and install rollup 7 :(

Do you see any erros in Application log on the server? If not can you please bounce the diagnostics logging on MSExchange ADAccess\Recipient Update ServiceMSExchangeAL\Ldap OperationsMSExchangeAL\Service Control andMSExchangeAL\Attribute Mappingto maximum and see if it logs any errors for you in application logs?Milind Naphade | MCTS:M | http://www.msexchangegeek.com

Source: MSExchangeALCategory: LDAP OperationsEvent ID: 8026 LDAP Bind was unsuccessful on directory (server).(domain).com for distinguished name ''. Directory returned error:[0x51] Server Down.I honestly believe this is a red herring. All Exchange services are in a started status.This server is one we configured as a domain controller, not a global catalog controller mind you, and will be shipping this overseas. We've done this before with no errors.The server in question is also not configured anywhere in exchange or in windows 2003 hosting exchange.set command shows we are indeed connected toa primary global catalog server and not the one in the error.

Even though all Microsoft Exchange services were showing a started status, restarting the Microsoft Exchange System Attendant did the trick and I am now able to create a new user and add a mailbox to an existing user.And yes, I double checked the logs and a reboot was performed after installing rollup 8.

I am glad to see that it is working for you now. If you see the error correctly it says the LDAP bind to the directory server was unsuccessful. That points to a problem with communication with DC/GC. AL services is still a part of MSExhangeSA. Till the time your system attendant is not in good shape the AL service wont work the way it is supposed to.Milind Naphade | MCTS:M | http://www.msexchangegeek.com

Even though all Microsoft Exchange services were showing a started status, restarting the Microsoft Exchange System Attendant did the trick and I am now able to create a new user and add a mailbox to an existing user.And yes, I double checked the logs and a reboot was performed after installing rollup 8. Terressa, I noted that I restarted the System Attendant in my original post and that this acted only as a temporaryworkaround. Can you please confirm the following for me ? Are you still intermittently having the same problem or has restarting the above SA service acted as a permanent fix ? When you can't create a new mailbox, are you receiving the same error message I mentioned in my original post ? Look forward to your response :-) "Keep a cool head and always carry a lightbulb."

Do you see any erros in Application log on the server? If not can you please bounce the diagnostics logging on MSExchange ADAccess\Recipient Update ServiceMSExchangeAL\Ldap OperationsMSExchangeAL\Service Control andMSExchangeAL\Attribute Mappingto maximum and see if it logs any errors for you in application logs? Milind Naphade | MCTS:M | http://www.msexchangegeek.com Hi Milind. I've run the following four commands: set-eventloglevel -Identity 'MSExchange ADAccess\Recipient Update Service' -Level expert set-eventloglevel -Identity 'MSExchangeAL\LDAP Operations' -Level expert set-eventloglevel -Identity 'MSExchangeAL\Service Control' -Level expert set-eventloglevel -Identity 'MSExchangeAL\Attribute Mapping' -Level expert However, you mentioned 'bouncing' something. Do I need to restart a service for the logging level changes to take effect ?"Keep a cool head and always carry a lightbulb."

Hello Huddie,No, you dont need to restart the services. Once you are done with increasing the logging level on all those services then you should be good to go and see the logs in event logs. Did you try creating a new user account after you have increased (in my words, bounced) the logging on given parameter? If not yet, then go ahead and try creating one. Additinally, you should also check to see if you see any warnings or errors related to MSExchangeSA.MMilind Naphade | MCTS:M | http://www.msexchangegeek.com

Hello Huddie,No, you dont need to restart the services. Once you are done with increasing the logging level on all those services then you should be good to go and see the logs in event logs. Did you try creating a new user account after you have increased (in my words, bounced) the logging on given parameter? If not yet, then go ahead and try creating one. Additinally, you should also check to see if you see any warnings or errors related to MSExchangeSA.M Milind Naphade | MCTS:M | http://www.msexchangegeek.com Thanks Milind. Unfortunately, it's an intermittent problem and, at the moment, accounts are creating successfully. When account creation stops working again I'll check the logs and report back. Intermittent problems are a bummer :-("Keep a cool head and always carry a lightbulb."

Late to respond, but try this... Go to your exchange server: Start, Run, CMD, Enter Type Ntdsutil, Enter Type LDAP policies, Enter Type connections, Enter Type connect to server "your DC with master roles", Enter ---should say binding to "your DC with master roles" Type quit, Enter Type quit, Enter Type quit, Enter Type exit, Enter Try making the change to Exchange now.

Thanks Big R (and Milind). I think this issue's still happening, however, I need to check again as I've not created many mailboxes in a while and recent creation attempts have been successful. Will post logs and try Big R's suggestion if the issue happens again."Keep a cool head and always carry a lightbulb."